-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update EIP-7748: fix namings #8780
Conversation
Signed-off-by: Ignacio Hagopian <[email protected]>
✅ All reviewers have approved. |
Signed-off-by: Ignacio Hagopian <[email protected]>
class BasicDataPhase: | ||
class AccountDataPhase: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With @gabrocheleau, we decided to rename it AccountDataPhase
since BasicDataPhase
is a bit off, considering that in VKT, it usually leaves out the code-hash (which, in case of the migration, is also moved).
We'd like at least one extra approval for this renaming (or new suggestion!) from another author.
cc @gballet @g11tech @tanishqjasoria
(Note: avoiding switching from Draft to avoid automerge)
Signed-off-by: Ignacio Hagopian <[email protected]>
Signed-off-by: Ignacio Hagopian <[email protected]>
Signed-off-by: Ignacio Hagopian <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I actually wonder if AccountPhase
wouldn't be better, since "account data" could be interpreted as "account storage".
Thing is that I agree that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All Reviewers Have Approved; Performing Automatic Merge...
This PR fixes:
BasicDataPhase
, since as mentioned by @gabrocheleau it might create some confusion since the semantics ofBasicData
are different in VKT.